Nectar Logo

User-Centred Requirements Handbook

Telematics Engineering Logo

Part C: 4. User Requirements Methods


4.18 Walkthroughs

What Is The Method, And When Can It Be Used?

A walkthrough is a process of going step by step through a system design getting reactions from relevant staff, typically users. Normally one or two members of the design team will guide the walkthrough, while one or more users will comment as the walkthrough proceeds

Benefits

• Obtains reactions to a design in an informal manner.

• Flexible means of obtaining reactions, allowing the users' discussion to range over issues not originally considered.

Limitations

• Requires some form of prototype to show and for user to react to.

• Results are opinions rather than objective data.

• Users may tend to react positively on seeing some prototype in operation.

• It may be difficult to imagine how the system will operate in the real environment.

What you need

Requires a prototype to be developed. The time overhead in holding the walkthrough sessions largely depends upon the task domain and the number of users exposed to the prototype.

Process

The general procedure for implementing this method is outlined in the following.

1. Decide clearly what issues or task scenarios should be covered by the walkthrough.

2. Set up a good recording mechanism, e.g. one person to show the system and ask questions, another to take notes, or record on tape, people's comments for transcription later on.

3. Select appropriate users to take part in the walkthrough, trying to cover the range of users within the target population.

4. Pilot the walkthrough to work out how much time is needed for each session.

5. Ensure recording facilities are available and functioning.

6. Conduct the walkthrough sessions, making sure that all sessions cover the issues identified beforehand.

7. Analyse information obtained by issues raised and comments made. Try to determine how many users made the same comment. Consider the themes and severity of the problems identified.

Practical guidelines

• Give an introduction to the participants in the walkthrough, explaining the aims of the session.

• Describe beforehand the range of tasks being covered.

• Allow enough time to discuss different aspects in depth.

• Explain that the participants should not be afraid to criticise the system.

• Encourage all participants to express their opinions.

• Consider audio recording the session and transcribing the information afterwards. This will allow the walkthrough to proceed more steadily.

Further information

Maulsby, Greenberg and Mander (1993), Nielsen (1993).


4.19 Wizard of Oz prototyping
Back to Contents

NECTAR Home Page The NECTAR Information Update The NECTAR Repository The European Journal of Engineering for Information Society Applications The NECTAR Discussion Fora